Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Jun 9, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^18.0.1^19.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-31051

Impact

What kind of vulnerability is it? Who is impacted?

Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.

Patches

Has the problem been patched? What versions should users upgrade to?

Fixed in 19.0.3

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Secrets that do not contain characters that are excluded from encoding with encodeURI when included in a URL are already masked properly.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:


Release Notes

semantic-release/semantic-release (semantic-release)

v19.0.3

Compare Source

Bug Fixes
  • log-repo: use the original form of the repo url to remove the need to mask credentials (#​2459) (58a226f), closes #​2449

v19.0.2

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the stable version (0eca144)

v19.0.1

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the latest beta version (8097afb)

v19.0.0

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
  • upgrade marked to resolve ReDos vulnerability (#​2330) (d9e5bc0)
BREAKING CHANGES
  • npm-plugin: @semantic-release/npm has also dropped support for node v15
  • node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-terminal that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from latipun7 as a code owner June 9, 2022 23:57
@renovate renovate bot added dependencies Pull requests that update a dependency file security labels Jun 9, 2022
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 47d6fb9 to 3ff3a25 Compare March 18, 2023 23:52
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from d0c0fbe to 73380eb Compare August 13, 2025 16:13
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 73380eb to 4e8b6a9 Compare August 19, 2025 17:48
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4e8b6a9 to 1aceec5 Compare September 25, 2025 16:27
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 1aceec5 to 143696a Compare October 21, 2025 22:40
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 143696a to fdf0af3 Compare November 11, 2025 01:01
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from fdf0af3 to 4b187a5 Compare December 31, 2025 14:57
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4b187a5 to 754f957 Compare January 19, 2026 17:53
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 754f957 to 1c142e6 Compare February 2, 2026 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants